| ||||||||||||||||||
| |||||||||||||||||||
 |
|
|
| Read this before any use of these guidelines | Contents | |
|
These guidelines contain information and instructions for the GEM hardware used in TSP 3. If Carmencita hardware is used in TSP 3, please refer to the official document 1/1532-APZ 302 02/1 and 2/1532-APZ 302/1 (H-Module).
These guidelines should not be regarded as official Ericsson documentation, since they are written mainly for my own use. However, if they suit your needs, feel free to use them. Of course, you should always use the official TelORB O&M documentation, but if you get stuck, these guidelines might come in handy. Keep in mind that these guidelines, as well as some of the linked pages below, reflect the UAB environment and that these guidelines are continuously being updated on a daily basis. Disclaimer
I do not take any responsibility for erroneous handling of a TelORB system as the result of following these guidelines. Your feedback and suggestions for improving these guidelines are very much appreciated; send an e-mail to Andreas Johansson. No alcohol was consumed during the writing of these guidelines. 
|
| Contents | Top | |
|
|
|
|
| GEM hardware in TSP 3 | Contents | |
GeneralIn TSP 3, a new type of hardware platform is introduced, even if the old Carmencita hardware can be used. The hardware is called GEM (Generic Ericsson Magazine) and is used in other Ericsson products as well. The idea is to have one generic magazine that can be used for a number of different products.
A maximum TSP 3 configuration.
ConfigurationA number of different configurations (number of processors) exist for the hardware in TSP 3. The smallest has only a few processors and the largest consist of the following, see the picture as well:
NotesTSP 3 on GEM hardware will never be delivered to external customers, it will only be used inside Ericsson to develop applications. The next release of the product, TSP 4, will be sold to real customers. That means that the hardware configuration layout for TSP 3 does not follow a strict standard in some lab sites.A configured TSP 3 system must follow the following rules:
|
| Description of all units | Contents | |
| On the next pages are all units inside the system described in alphabetical order. |
| Cabinets | Contents | |
GeneralOne or two cabinets can be present depending on how big system (number of traffic processors) that will be used. The type of the cabinet is the normal BYB 501. |
| Cable Shelf | Contents | |
GeneralFive cable shelves of two different sizes are included in each cabinet. |
| Fan | Contents | |
GeneralFront view of the fan. The fans will cool the system as well as monitor the temperature and, if necessary, generate temperature alarm(s). One fan is located above each magazine, which gives four fans in a cabinet. Serial cooling is used, i.e. the air is sucked into the system at the bottom of the cabinet, passing all equipment before it is blown out at the top. A fan is powered with -48V from two sources, "Power A -48V" and "Power B -48V". If one of the powers is failing, the fan still fully functioning and an alarm is raised. Three fans are located inside a fan unit. If a problem occur on one or more of them, an alarm is raised. The speed of the fans depends on the air temperature passing the fan unit, i.e. an increasing temperature makes the speed on the fans to increase. AlarmsThe connector "Supervision" is used to connect the fan with the left SCB in the magazine below. This connection (V24) is used to report alarms from the fan to the SCB, which is reporting all hardware alarms to the Dicos OS. To be able to know which fan that is generating an alarm, the name of the reporting SCB is included in the alarm data.To following alarms can be generated from each fan:
NotesThe "Supervision extension" connector is not used in TSP 3, it is used if more fans are connected to one SCB.The MIA lamp is not used in TSP 3. Because the cabinet has serial cooling it is not a serious problem if one of the fans should stop. The system will, under normal circumstances, work as normal. But of course, it is needed to solve the problem as soon as possible. |
| Filter | Contents | |
GeneralThis filter is a combined air filter and a filter that is stopping hot material to fall down from the cabinet in case of a fire. It should be removed and cleaned with regular intervals. |
| GESB, Gigabit Ethernet Switch Board | Contents | |
GeneralFront viewof a GESB.  
The task for the GESB (Gigabit Ethernet Switch Board) is to connect the ethernet networks inside all magazines to each other. This is done by an ethernet switch , with eight 1 Gb/s ports, inside the GESB. All communication between the GESB and the magazines are 1Gb/s while 100Mb/s is used internally inside the magazines. The interface to the magazine is the "1000BaseT" port on the SCBs.
Two GESB are needed because it exist two internal networks inside the magazines.
As said before it exist eight 1Gb/s ports ("0" to "7") on the GESBs. So, it is possible to connect eight magazines to each other. It exists two internal networks in the TSP 3 system. They are called traffic networks (or internal networks) A and B (or 1 and 2). See section Schematic ethernet connection in TSP 3 below. How to connect the SCBs to the GESBsHere is list how the GESBs and the SCBs are connected to each other, also see the section Cabling.
GESB-A (in magazine 2):
GESB-B (in magazine 3):
Monitor the GESBTo be able to monitor the GESB must the IP addresses be set on the board, see section Notes below.Telnet is used log in to the GESB. A command based interface is used to monitor all ethernet ports on the board. See section Monitor SCB / GESB below. NotesThe MIA lamp is not used in TSP 3.In TSP 3 it does not exist any function to monitor the 1Gb/s links between the GESBs and the SCBs. So, if a GESB or a cable between a GESB and a SCB is failing, no alarm what so ever is raised. This will be fixed in TSP 4. Two IP addresses should be set in all GESBs to be able to monitor them. In TSP 3 it does not exist any way to set those addresses. In future releases will the DHCP function in the SPs together with the physical positions of the GESBs be used to set the IP addresses. It exist a work around to fix this problem in TSP 3, see section Set IP addresses in SCB / GESB below. All ports on the GESB are automatically recognizing the polarity of the port at the other end of the cable. So, it is not necessary to use any twisted (or null modem) ethernet cables, the board will take care of that. Schematic ethernet connection in TSP 3Schematic ethernet connection.(Click on the picture to enlarge) 
|
| Magazine | Contents | |
GeneralA GEM (Generic Ericsson Magazine) has 26 slots (or positions) where slot 0 (leftmost) and slot 25 (rightmost) are reserved for SCBs. The rest, slot 1 to 24 can be used for processor boards. The distance between two slots is 15 millimeters. The width of a traffic processor in TSP 3 is 30 millimeters so it is possible to insert maximum 12 traffic processors in a magazine in TSP 3.Each one of those slots will have two ethernet connections, one operation and maintenance connection and dual power connection. Cooling is received from the fan located just above. Ethernet buses in the backplane
Power buses in the backplane
Address bus in the backplane
Magazine numberingFour magazines are mounted in a cabinet. The following magazine numbering is used in TSP 3:
Magazine addressingThe address plugs inserted in the address positions has the product number TVJ 119 1111/xx, where the suffix is the number that will be read by the system.Here is an example of with address plugs that can be used in a maximum configured TSP3 system. The node number can be change on different nodes.
Slot position vs. physical positionA magazine contains of 26 slots. A magazine is also divided into 86 parts horizontally, this physical dividing is shown at the top and bottom of the magazine. The following table is showing on which physical position all slots are located. See also the section Numbering below.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Patch panel | Contents | |
GeneralFront view of a Patch Panel.
All external cabling (except power cables) will be connected to/from the system via a patch panel. Magazine 2 in both cabinets are housing a patch panel which is divided into two parts. The lower part is connecting all necessary units inside the system to the patch panel. This cabling is done during the assembling of the cabinet.
All external cables shall be connected to the connectors in the upper part. It is possible to connect 40 cables to each cabinet, see picture. Meaning of the connectorsThe connectors in the patch panel has the following functions:
NotesIt is a straight connection between a connector in the lower part and the same connector in the higher part, i.e. no intelligence or electronics is added on the patch panel board.The MIA lamp is not used in TSP 3. |
| SCB, Switch Control Board | Contents | |
GeneralAn SCBs (Switch Control Board) are located in both ends of each magazine. In TSP 3 those have the following tasks:
Ethernet SwitchAn ethernet switch is housed inside the SCB. Duplicate ethernet buses exist among other things in the backplane of the magazine. The ethernet switch in the SCB at the leftmost position in the magazine is controlling one of those buses, the rightmost the other bus.The ethernet switch has 26 100Mb/s ports towards the backplane. Two of them are used by the both SCBs. So, up to 24 units (processors) can be inserted in the magazine and receive dual ethernet connections. Also one 100Mb/s port and one 1Gb/s port are located at the front of the board. With those ports is it possible to connect the networks in the backplane to the outside world. Due to a misunderstanding during the design phase of the TPs in TSP 3 is the first traffic network (net 1 or net A) controlled by SCBs to the right side of a magazine. For an overview picture of the networks in TSP 3 take a look at the picture Schematic ethernet connection in TSP3. Power SuppliesThe SCB is also responsible for the power distribution inside the magazine. Two -48V power cables are feeding each SCB, they are connected to the connectors "-48V L" and "-48V R" from the same power source.The SCB is filtering the power before it redistribute the -48 V to the backplane via fuses. "-48V L" on both SCBs in a magazine are feeding the left half of the magazine, "-48V R" the right half. The SCB itself is powered from the backplane, i.e. if both power inlets are disconnected, the SCB is still running, feed by the other SCB, and alarms are generated. Ethernet interfacesThe 1Gb/s link, "1000BaseT", is used to connect the SCB to the GESB, see section GESB and Cabling .If the function network redundancy is used the network redundancy links should be connected to the 100 Mb/s link, "100BaseTx", at the front of the SCBs in magazine 2, see section Cabling . The CPU in the SCB has two ethernet interfaces to both internal networks. The port "eth1" is connected to traffic network A (right SCB) while the port "eth0" is connected to traffic network B (left SCB). AlarmsTo be able to have the alarm function to work must the IP addresses be set on the SCB, see section Notes below.All SCBs in the system are collecting and reporting hardware related alarms. All leftmost SCBs are also reporting fan related alarms since they are connected to the fan just above, via the port "V24". The Dicos OS has SNMP contact to all SCBs via both traffic networks by use of a symbolic name, (environment parameter "GEM_SCB_ADDRESSES"). That name is translated into two IP addresses by DNS function inside TelORB. Any names for the SCBs can be used but in our TelORB lab have we used the following names:
The hardware alarms that can be generated are fan and temperature related alarms, see section Fan above, and the two following power alarms:
Monitor the SCBTo be able to monitor the SCB must the IP addresses be set on the board, see section Notes below.Telnet is used log in to the SCB. A command based interface is used to monitor all ethernet ports on the board. See section Monitor SCB / GESB below. NotesThe "TEST" connector is not used in TSP 3. In later releases will it be used as a ethernet test channel into the system.The "EXT ALARM" connector is not used in TSP 3. In later releases will it be possible to connect one external alarm per SCB. The SCB is used in the AXE world as well, there are the connectors "RPB-S/x" used but they are not used in TSP 3. The MIA lamp is not used in TSP 3. To get the alarm monitoring to work must some environment parameters be specified, see section epct setting for GEM HW below. Because the SCB has a lot of pins to the backplane is it very sluggish to insert and remove the board. To ensure proper connection to the backplane both screws should be tighten firmly. Two IP addresses should be set in all SCBs to have the alarm and monitoring function to work. In TSP 3 it does not exist any way to set those addresses. In future releases will the DHCP function in the SP's together with the physical positions of the SCBs be used to set the IP addresses. It exist a work around to fix this problem in TSP 3, see section Set IP addresses in SCB / GESB below. All ethernet ports (except "TEST") on the SCB are automatically recognizing the polarity of the port at the other end of the cable. So, it is not necessary to use any twisted (or null modem) ethernet cables, the board will take care of that. |
| SP, Support processor | Contents | |
General
Adapter boardSchematic picture of the SP unit.
The main task for the adapter board is to make it possible to connect the processor to the backplane. The processor, which is bought from an external supplier, is using a cPCI (Compact Peripheral Component
Interconnect) standard in its connectors. The GEM does not supply cPCI standard. So, one of the functions on the adapter board is to convert from cPCI to GEM.
Power suppliesThe dual -48V power sources on the backplane of the GEM is transformed to -12V, 3.3V, 5V and 12V (???) by the power supplies on the adapter board. The power supplies is still operating if one of the power sources fails.CPUThe CPU on the adapter board has a lot of functions, but in TSP 3 is the CPU only used to monitor the temperature on a temperature sensor, which is mounted on the heat sink of the processor. If the temperature reach 80 °C (???), will the CPU shut down the power supplies on the adapter board. The CPU is turning on the power supplies again when the temperature is decreasing to 75 °C (???).Processor boardThe processor used in the SPs are Sparc, cPCI-540, processors running on 440 MHz and the internal memory is 512 Mbyte.Hard disksEach SP has to 18,2 Gbyte hard disks connected on a SCSI bus to the processor.DVD/TapeSP-2 has also a DVD reader and a tape writer/reader connected on the SCSI bus. Those units are located under a special EMC (Electro Magnetic Compatibility) cover.Serial interfaceTwo serial interfaces are present on each SP. Serial A interface on SP1 and SP2 is reserved for modem communication towards the system. All other serial interfaces can be used for example trouble shooting. The data towards the interfaces is:Baud rate: 9600
Ethernet interfaces"100BaseT" connector is the ethernet connection to the outside world from the system. In Solaris this port is called "fciprb1".Two ethernet ports (10/100 Mb/s ) are via the backplane connected to ethernet switches in both SCBs. The port "fciprb0" is connected to traffic network A (right SCB) while the port "hme0" is connected to traffic network B (left SCB). ButtonsThe buttons "RESET" and "ABORT" is used to restart respectively stop the processor. Those should not be used in normal operation, due to risk of damaging the UNIX file system.LampsSee section Notes below.NotesThe MIA lamp is not used in TSP 3.It exists one extra ethernet port (number 4 in the picture) on the front of each SP. This port shall not under any circumstance be used. Because the software in the processor can handle three ethernet ports "fciprb0", "fciprb1" and "hme0". But the hardware has four ethernet ports, two at the back and two at the front of the board. "hme0" can be used either at the front or at the back of the board, depending which port that has an ethernet connection during start up. So, if a cable is connected to port number 4 (in picture) can "hme0" be located in the front instead of the port to the backplane. As described in section Lamps below only a MIA lamp should be used on each unit. Due to production circumstances more lamps and contacts are visible on the SPs. They have no labels because they should not be there but they have the following meanings (see picture above):
|
| TP, Traffic processor | Contents | |
General
Adapter boardSchematic picture of a TP unit.
The main task for the adapter board is to make it possible to connect the processor to the backplane. The processor, which is bought from an external supplier, is using a cPCI (Compact Peripheral Component Interconnect) standard in its connectors. The GEM does not supply cPCI standard. So, one of the functions on the adapter board is to convert from cPCI to GEM. Power suppliesThe dual -48V power sources on the backplane of the GEM is transformed to -12V, 3.3V, 5V and 12V (???) by the power supplies on the adapter board. The power supplies is still operating if one of the power sources fails.CPUThe CPU on the adapter board has a lot of functions, but in TSP 3 is the CPU only used to monitor the temperature on a temperature sensor, which is mounted on the heat sink of the processor. If the temperature reach 80 °C (???), will the CPU shut down the power supplies on the adapter board. The CPU is turning on the power supplies again when the temperature is decreasing to 75 °C (???).Processor boardThe processor used in all TPs are pentium processors, MXP64GX from Teknor, 700 MHz and 1 Gbyte RAM.Ethernet PMC boardSS7 PMC boardThe TPs consist of the following:
Serial interfaceOn each TP is a serial interface "V.24" present, which can be used for example trouble shooting. The data towards the interfaces is:Baud rate: 38400
Ethernet interfacesTwo ethernet ports (10/100 Mb/s) are connected via the backplane to each SCB. The port "eth0" is connected to traffic network A (right SCB) while the port "eth1" is connected to traffic network B (left SCB). Due to a misunderstanding during the design of the adapter board the two interfaces were swapped. The most logical way should be to have net A to the left and net B to the right.In each TPIP a PMC module with two ethernet ports is added to a normal TP. The lowest port is "eth2" and the highest is "eth3". SS7 interfacesIn each TPSS7 a PMC module with four SS7 ports is added to a normal TP. Each SS7 port is a E1/T1 SS7 link which can be divided into 24 (T1) or 32 (E1) channels. Due to processor capacity maximum of 32 channels can be transmitted via the PCI bus into the processor. ButtonsThe "RESET" button is used to restart the processor. This should not be used in normal operation. LampsSee section Notes below.NotesThe MIA lamp is not used in TSP 3.As described in section Lamps below only a MIA lamp should be used on each unit. Due to production circumstances more lamps are visible on the TPs. They are located under the V24 connector, but they have no labels because they should not be there but they have the following meanings: Left. Blue = The processor is ready to remove(Hot Swap). Not used in TSP 3.
|
| Various useful descriptions | Contents | |
GeneralOn the following pages some useful notes, information, descriptions and "how to do" are mentioned, which can be handy to know when working with GEM hardware. |
| Remove and insert boards | Contents | |
GeneralNo space exist between a magazine and the cable shelve(s) just over or below the magazine. So, when a board should be removed from the magazine it is not enough to disconnect the cables to that board. All disconnected cables are running into the cable shelf in front of the board. Because lack of space it is impossible to bent those cables so they are not in the way when the board is removed. Instead is it necessary to open the cable shelf and remove those cables. An easier way exist if not so many cables, press the cable shelf hard away from the magazine.Be sure that the boards next to a board that will be removed is screwed to the magazine. Otherwise can the neighbor board(s) be pulled out as well because it is so tight between boards in the GEM. To ensure proper function should all boards be screwed tight to the magazine, especially the SCB. |
| Contacts | Contents | |
GeneralTo ensure a safety EMC protection all connectors shall be of the Concept type (or Sofix type). Today, most the connectors are of that type but some are of the type RJ45 and USB. Those will be changed to Concept connectors in later releases. It also exists D-sub connectors, those will not be changed to Concept because they are only used for test and fault finding purposes. |
| Lamps | Contents | |
GeneralDue to Ericsson standard no other lamps than the MIA (Manual Intervention Allowed) should be visible on the front of a board. The idea is that the MIA lamp should be on when the board needs to be changed. The lamp can still be controlled if the power on the board fails. All other lamps could confuse the personnel. Different opinions about this exist.Anyhow, due to production circumstances more lamps are visible on some boards. |
| Power | Contents | |
GeneralAll power distribution inside the system is described in the section SCB above. How the power is coming in to the system is described here.A cabinet consists of four magazines with a fan just above each magazine. A magazine/fan is feed with -48V from both ends. One -48V power cable is connected to the power distribution in the building. The other end is split into three connectors. Two of these connectors are mounted to one SCB, the third is connected to the fan. A second cable is connected in the same way but to the other side of the magazine/fan. A ground cable to each cabinet is also necessary to connect. So two -48V power cables are needed for each magazine. That will be eight cables per cabinet. In our TelORB lab we have been using four 16A fuses instead of the official 8, it was no problem at all. |
| Cabling | Contents | |
|
Picture of the cableling for a maximum TSP 3 system.
(Click on the picture to enlarge) 
GeneralHave a look at the picture to get an overview for the cabling in TSP 3.All cables which are connecting units inside the system to each other, are connected directly between the units. The power cables are connected directly to the power distribution. The rest of the cables are connected via the Patch panel, which is not showed in the picture. NoteOn the SCBs and Patch panel it is possible to connect cables for external alarms. External alarms is not included in TSP 3, so no cable are needed on those positions. |
| Numbering | Contents | |
GeneralThe numbering principle in a system on GEM hardware is that the numbering should starts on 0 (zero) in the lower left corner. In TSP 3 is that principle mostly used but not in all cases, here is a list where the numbering differ from the principle.
Position numberingPicture of position numbering in GEM.(Click on the picture to enlarge) 
To be able to find a physical position in a GEM system, the following three position numbering are used.
As an example, a label with a position can look as follow:
The position information has the following meaning:
NotesThe "Gem position 1 to 24" in the picture are all positions in the magazine with connection to dual ethernet connections, dual power connection and a O&M connection is available. In TSP 3 are not all of those positions used. |
| Product numbers and useful documentation | Contents | |
GeneralI have tried to include most of the necessary things to know about the hardware in TSP 3 in these guidelines. A lot more information can be found in the official documentation for the different units in the hardware.In the list below are the most essential hardware products showed in a product structure layout. All product numbers are showed, which makes is easier to search for more information about the product. I have links to, what I think, some good documents. Those documents is "OPEN", i.e. everyone inside Ericsson has the right to read them. Products can change over a period of time and I will not check that I have links to the latest documents on a regular basis. So it can happen that the information below is not accurate. If a product exist in both first and second cabinet is any related documentation only showed together with the first cabinet. Product numbers and some good documents for the hardware in TSP 3
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Set IP addresses in SCB / GESB | Contents | |
GeneralTo be able to have the hardware alarm function and the monitoring (of SCB and GESB) functions to work must all SCBs and GESBs have two IP addresses, one for each internal network.In TSP 3 it does not exist any function to distribute those addresses. In future releases will the DHCP function in the SP's together with the physical positions of the SCBs and GESBs be used to set the IP addresses. Here is a procedure to manually solve this problem. This solution is nearly the same that will be used in future releases but then is the data set up automatically. How to doHere is an explanation how to make the DHCP function to distribute the IP addresses to the SCBs and GESBs depending on their physical position.
NotesThe file "/opt/telorb/etc/dhcpd.pxe.conf" is overwritten when the script "opt/telorb/codearchive/iom_scripts/configureTelORB.sh" is run. When this script is run must the above mentioned procedure be done again.Two address plugs has to be inserted in each magazine to have the "position to IP address" function to work. Those should be in address position 1 and 3, see section Magazine above and the explanation below. Here is an explanation of the position identifier used by the DHCP function.
"0.1.255.0:eth0.1" (DHCP identifier)
!---- eth1.1 is the ethernet port to internal network A
eth0.1 is the ethernet port to internal network B
!-------- Position in the magazine.
0 is the position for the left SCB
25 is the position for the right SCB
23 is the position for the GESBs
!----------- The value of the address plug in address position 0 (highest)
in the magazine. If no address plug is used is the value 255
!-------------- Magazine number (0 to 4). This is the value of the address
plug in position 1 (third from bottom)
!---------------- Node number. This is the value of the address plug in
position 3 (lowest)
ExampleHere is the complete configuration data for SCB and GESB IP set up in a fully equipped TSP 3 system.Not used magazines and equipment can be removed before this data is inserted in your system. Of course must the IP addresses be changed so it mach your system. When copying from the example below, do not forget the last parenthesis.
*****EXAMPLE********************************************************************
Group {
#Set the time the SCB/GESB shall remember the IP address to infinite
default-lease-time = ff:ff:ff:ff;
max-lease-time = ff:ff:ff:ff;
filename = "";
########## Magazine 0 (lowest in base cabinet) ###################
########## SCB_0A (Left SCB) ##########
##### Eth to net A ######
host SCB_0A_netA {
option dhcp-client-identifier = concat(00,"0.0.255.0:eth1.1");
fixed-address 134.138.76.10;
}
##### Eth to net B ######
host SCB_0A_netB {
option dhcp-client-identifier = concat(00,"0.0.255.0:eth0.1");
fixed-address 134.138.77.10;
}
########## SCB_0B (Right SCB) ##########
##### Eth to net A ######
host SCB_0B_netA {
option dhcp-client-identifier = concat(00,"0.0.255.25:eth1.1");
fixed-address 134.138.76.11;
}
##### Eth to net B ######
host SCB_0B_netB {
option dhcp-client-identifier = concat(00,"0.0.255.25:eth0.1");
fixed-address 134.138.77.11;
}
########## Magazine 1 (second from bottom in base cabinet) ##########
########## SCB_1A (Left SCB) ##########
##### Eth to net A ######
host SCB_1A_netA {
option dhcp-client-identifier = concat(00,"0.1.255.0:eth1.1");
fixed-address 134.138.76.12;
}
##### Eth to net B ######
host SCB_1A_netB {
option dhcp-client-identifier = concat(00,"0.1.255.0:eth0.1");
fixed-address 134.138.77.12;
}
########## SCB_1B (Right SCB) ##########
##### Eth to net A ######
host SCB_1B_netA {
option dhcp-client-identifier = concat(00,"0.1.255.25:eth1.1");
fixed-address 134.138.76.13;
}
##### Eth to net B ######
host SCB_1B_netB {
option dhcp-client-identifier = concat(00,"0.1.255.25:eth0.1");
fixed-address 134.138.77.13;
}
########## Magazine 2 (third from bottom in base cabinet) ##########
########## SCB_2A (Left SCB) ##########
##### Eth to net A ######
host SCB_2A_netA {
option dhcp-client-identifier = concat(00,"0.2.255.0:eth1.1");
fixed-address 134.138.76.14;
}
##### Eth to net B ######
host SCB_2A_netB {
option dhcp-client-identifier = concat(00,"0.2.255.0:eth0.1");
fixed-address 134.138.77.14;
}
########## SCB_2B (Right SCB) ##########
##### Eth to net A ######
host SCB_2B_netA {
option dhcp-client-identifier = concat(00,"0.2.255.25:eth1.1");
fixed-address 134.138.76.15;
}
##### Eth to net B ######
host SCB_2B_netB {
option dhcp-client-identifier = concat(00,"0.2.255.25:eth0.1");
fixed-address 134.138.77.15;
}
########## GESB_A ##########
##### Eth to net A ######
host GESB_A_netA {
option dhcp-client-identifier = concat(00,"0.2.255.23:eth1.1");
fixed-address 134.138.76.20;
}
##### Eth to net B ######
host GESB_A_netB {
option dhcp-client-identifier = concat(00,"0.2.255.23:eth0.1");
fixed-address 134.138.77.20;
}
########## Magazine 3 (highest in base cabinet) ##########
########## SCB_3A (Left SCB) ##########
# Ethernet interface to internal network A.
host SCB_3A_netA {
option dhcp-client-identifier = concat(00,"0.3.255.0:eth1.1");
fixed-address 134.138.76.16;
}
# Ethernet interface to internal network B.
host SCB_3A_netB {
option dhcp-client-identifier = concat(00,"0.3.255.0:eth0.1");
fixed-address 134.138.77.16;
}
########## SCB_3B (Right SCB) ##########
##### Eth to net A ######
host SCB_3B_netA {
option dhcp-client-identifier = concat(00,"0.3.255.25:eth1.1");
fixed-address 134.138.76.17;
}
##### Eth to net B ######
host SCB_3B_netB {
option dhcp-client-identifier = concat(00,"0.3.255.25:eth0.1");
fixed-address 134.138.77.17;
}
########## GESB_B ##########
##### Eth to net A ######
host GESB_B_netA {
option dhcp-client-identifier = concat(00,"0.3.255.23:eth1.1");
fixed-address 134.138.76.21;
}
##### Eth to net B ######
host GESB_B_netB {
option dhcp-client-identifier = concat(00,"0.3.255.23:eth0.1");
fixed-address 134.138.77.21;
}
########## Magazine 4 (lowest in the extension cabinet) ##########
########## SCB_4A (Left SCB) ##########
##### Eth to net A ######
host SCB_4A_netA {
option dhcp-client-identifier = concat(00,"0.4.255.0:eth1.1");
fixed-address 134.138.76.18;
}
##### Eth to net B ######
host SCB_4A_netB {
option dhcp-client-identifier = concat(00,"0.4.255.0:eth0.1");
fixed-address 134.138.77.18;
}
########## SCB_4B (Right SCB) ##########
##### Eth to net A ######
host SCB_4B_netA {
option dhcp-client-identifier = concat(00,"0.4.255.25:eth1.1");
fixed-address 134.138.76.19;
}
##### Eth to net B ######
host SCB_4B_netB {
option dhcp-client-identifier = concat(00,"0.4.255.25:eth0.1");
fixed-address 134.138.77.19;
}
}
*****END OF EXAMPLE*************************************************************
Old way to set the IP addressesBefore the above mentioned way to set the IP addresses was known the following way have to be used. Maybe this can be used in some lab sites so this information is kept.The following material is needed to set the IP addresses in the SCB and GESB:
Use the following settings:
Before starting, be sure the RPG Debug Terminal is connected to the flat cable and to the serial cable at connector "A". Also start your terminal program. How to do:
NotesIf you type something wrong and get an error result, the prompt is changed to "?>". To reset this so a normal operation is archived do the command:clear error If you want to remove the IP data that has been set according tp the above procedure, do the following.
|
| Monitor SCB / GESB | Contents | |
GeneralIt is possible to monitor the SCBs and GESBs. Telnet is used to log in to the board. A command based interface is used to check ethernet ports, software units etc. Two IP addresses must be set to be able to monitor the SCB/GESB, see section Set IP addresses in SCB / GESB above.LoginThe same login procedure is used on the SCB and the GESB. Username and password is set when the software is loaded into the board (???).
CommandsHere are some useful commands mentioned and explained.
Port numbering in the SCBEach SCB has 26 ports to the backplane and tree ports to the front of the board. The table below is describing which unit that is connected to each port number. The ports 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22 and 24 are not used in TSP 3.To see the status on ethernet port connected to traffic processor 6, login to one of the SCBs in magazine 0 and do the following command:
To see the status on the "1000BaseTx" ethernet port at the front of the SCB, login to that SCBs and do the following command:
Port numbering in the GESBInformation yet to come.Printout descriptionThis is an example of a printout ordered by the command "scbsw -mib -pX". Some notes (#) are added to clarify some output parameters.error : 0 GoodBytesRx: 91614884 GoodBytesTx: 125073636 GoodFramesRx: 1177994 GoodFramesTx: 1401203 TotalBytesRx: 91616344 TotalFramesRx: 1178014 BroadcastFramesRx: 4404 MulticastFramesRx: 0 CRCErrors: 0 OversizedFrames: 0 FragmentsRx: 0 JabberFramesRx: 0 Collisions: 0 LateCollisions: 0 Frames_64: 882655 Frames_65_127: 1561143 Frames_128_255: 126004 Frames_256_511: 1591 Frames_512_1023: 2837 Frames_1024_MAX: 4987 Reserved1: 0 FramesDropped: 0 MulticastFramesTx: 383130 BroadcastFramesTx: 93680 UndersizedFrames: 0 link_state: 1 # 1=up, 0=down link_speed: 1 # 0=10 Mbit/S, 1=100 Mbit/s duplex_mode: 1 flow_control: 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| epct setting for GEM HW | Contents | |
GeneralThe epct settings needed for the GEM is data for the hardware alarm function. It is data to load the software, also parameters to tell the Dicos OS about the hardware configuration is needed.SoftwareOnly one IDP is necessary to add to the system, namely:
ENVIRONMENT DATAFour parameters are added to inform the system about the HW configuration, those are the following:
INITIAL DATATo translate the name of the SCB into IP addresses are the following parameters used.
ExampleHere is an example used in a system, with 5 magazine, in our lab. When testing the hardware alarm function it is handy to reduce the time between polling to 1 second, "GEM_SCB_POLLINTERVAL = 1000". ENVIRONMENT DATA GEM_SCB_ADDRESSES = "SCB_0A,SCB_0B,SCB_1A,SCB_1B,SCB_2A,SCB_2B,SCB_3A,SCB_3B,SCB_4A,SCB_4B" GEM_SCB_FANUNITS = "1,0,1,0,1,0,1,0,1,0" GEM_SCB_MAXFANS = 1 GEM_SCB_POLLINTERVAL = 15000 ENDDATA INITIAL DATA SymbolicAddress_4 = "SCB_0A" NumericAddress_4 = "134.138.76.10:134.138.77.10" SymbolicAddress_5 = "SCB_0B" NumericAddress_5 = "134.138.76.11:134.138.77.11" SymbolicAddress_6 = "SCB_1A" NumericAddress_6 = "134.138.76.12:134.138.77.12" SymbolicAddress_7 = "SCB_1B" NumericAddress_7 = "134.138.76.13:134.138.77.13" SymbolicAddress_8 = "SCB_2A" NumericAddress_8 = "134.138.76.14:134.138.77.14" SymbolicAddress_9 = "SCB_2B" NumericAddress_9 = "134.138.76.15:134.138.77.15" SymbolicAddress_10 = "SCB_3A" NumericAddress_10 = "134.138.76.16:134.138.77.16" SymbolicAddress_11 = "SCB_3B" NumericAddress_11 = "134.138.76.17:134.138.77.17" SymbolicAddress_12 = "SCB_4A" NumericAddress_12 = "134.138.76.18:134.138.77.18" SymbolicAddress_13 = "SCB_4B" NumericAddress_13 = "134.138.76.19:134.138.77.19" ENDDATA |
| End of the page | Contents | |
each.
